Skip to content

Conversation

@Vysarat
Copy link
Contributor

@Vysarat Vysarat commented May 29, 2025

Summary: I'm working on a linter that checks a model's ops against those available in our runtime environment (see D75110565), and I'd like to call gen_oplist programmatically. I can't do that because gen_oplist_lib is not visible outside the executorch subdir. If there are no objections, I'd like to expose it to clients.

Differential Revision: D75630096

Summary: I'm working on a linter that checks a model's ops against those available in our runtime environment (see D75110565), and I'd like to call `gen_oplist` programmatically. I can't do that because `gen_oplist_lib` is not visible outside the `executorch` subdir. If there are no objections, I'd like to expose it to clients.

Differential Revision: D75630096
@pytorch-bot
Copy link

pytorch-bot bot commented May 29, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/11231

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 07c3daa with merge base 1f697f0 (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label May 29, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D75630096

@Vysarat Vysarat added topic: not user facing release notes: none Do not include this in the release notes labels May 29, 2025
base_module = "executorch.codegen.tools",
visibility = [
"//executorch/...",
"@EXECUTORCH_CLIENTS",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Im fine with this but you want a yaml? Would it be better if you refactored to take a dep on an in memory represenation?

@larryliu0820 Is this representation stable for people outside ET to take a dep?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree that skipping the yaml would make things cleaner. I think that can be fixed in a follow-up PR.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed let's do the hard work of exposing an API that returns the object in memory. Instead of a follow-up, can you do it first and it becomes clear on what library/target to expose publicly?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also just in general it seems like all you'd need are the dtype dim order combinations for every op

@facebook-github-bot
Copy link
Contributor

Hi @Vysarat!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

@github-actions
Copy link

github-actions bot commented Sep 1, 2025

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

@github-actions github-actions bot added the stale PRs inactive for over 60 days label Sep 1, 2025
@github-actions
Copy link

github-actions bot commented Nov 1, 2025

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported release notes: none Do not include this in the release notes stale PRs inactive for over 60 days topic: not user facing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants